Websydian Version 2.1 - What Is New?

• Full Support for Enterprise WAP Development
• Minor Changes and Enhancements
• Link to Version 2.1 Upgrade Guide

Full Support for Enterprise WAP Development

By version 2.1 of Websydian, full support for Enterprise WAP development can be purchased as an optional add-on module to the Websydian product.  The Websydian Enterprise WAP module includes:

• Introduction of Deck Generator and Card Generator patterns reflecting the structure of the WML (Wireless Markup Language).  Deck and Card Generators are analogous to the HTML Page Generators.
• Introduction of a Jump construct to model jumps between Cards within the same Deck.  This feature is a part of the WML standard.
• Further support of the WML standard by modelling of common actions (Event Handlers and Jump functions) for all Cards in a Deck in a special Template function suite.
• Full generation of WML Deck Templates from model definitions.  This feature will help getting the syntax of the generated WML Decks right.
• A number of WAP Utility patterns have been provided in a separate WAPUTIL pattern library.  These Utility patterns will help implementing a number of common design situations for Enterprise WAP applications.
• Description of how the existing Websydian modules (Session Management, Audit, Integrity Control and User Management) can be applied in Enterprise WAP applications.
• A WAP Tutorial guiding you through the development of a small WAP application.

Minor Changes and Enhancements

Since version 2.0, a number of minor modifications have been specified for Websydian.  Some of these modifications have been necessary in order to implement Websydian Enterprise WAP while other modifications are small enhancements and corrections of minor errors.

The modifications include:

• Full documentation has been provided for the Websydian ASP interface.
• The iSeries Java Servlet module has been removed from the product structure.  This change is due to future plans about upgrading the technical architecture.
• The PageGeneratorWithValueMapping pattern has been removed.  Instead, the functionality has been built into the ReplacementProcess pattern.
• Local fields in OmitDetailsFields and OmitGridFields variables must now be specified at Page Generator-level and not at Document Template Generator-level as before.
• The _DocumentTemplateGenerator pattern is now defined under the PageGenerator pattern and not under the ReplacementProcess pattern as before.
• Various patterns in the Websydian modules no longer contain a _DocumentTemplateGenerator function.  In this way, it is possible for the existing Websydian modules also to be used in Enterprise WAP development.
• Event Handlers will no longer result in a signature error when hidden status fields are transferred as parameters.
• Specifying the Charset in the Document Templates is now controlled by the developer.
• A number of new edit points have been added to the Document Template Generator.
• A boolean UseRow field has been introduced in the Page Generator making it possible to deselect records from the Grid.
• A minor error in the signature logic for Windows C++ implementations of the Integrity Control module has been corrected.  No work-arounds are needed anymore.

Link to Version 2.1 Upgrade Guide

When upgrading a Websydian model from version 2.0 to version 2.1, a few actions are necessary.  See the technical paper Upgrade Guide to Version 2.1 for the detailed steps to be performed when migrating a Websydian model from version 2.0 to 2.1.